rename rpc.response.status_code to rpc.status_code#3921
Open
lmolkova wants to merge 5 commits into
Open
Conversation
|
👋 Thanks for your contribution! This PR modifies file(s) in area(s) that do not currently have an active SIG/project:
Per the area ownership process, This does not mean your change is unwelcome:
Thanks again for taking the time to contribute! 🙏 |
Pull request dashboard statusStatus last refreshed: 2026-07-25 18:54:55 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the RPC semantic conventions by renaming the attribute rpc.response.status_code to rpc.status_code, reflecting that (e.g., in gRPC-compatible systems) the status code is not inherently a “response” property, and ensuring the model/docs stay consistent with the updated naming.
Changes:
- Rename the canonical RPC status code attribute to
rpc.status_codeand update references across RPC spans/metrics models and documentation. - Deprecate
rpc.response.status_codeas a renamed alias pointing torpc.status_code. - Add a breaking-change changelog entry for the rename.
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| model/rpc/spans.yaml | Updates span definitions to reference rpc.status_code instead of rpc.response.status_code. |
| model/rpc/registry.yaml | Renames the registered attribute id to rpc.status_code and updates its note text accordingly. |
| model/rpc/deprecated/registry-deprecated.yaml | Adds deprecated alias rpc.response.status_code renamed to rpc.status_code; updates other deprecated guidance to reference the new name. |
| model/rpc/common.yaml | Updates common RPC attribute references to rpc.status_code (note text still mentions “response status code”). |
| model/otel/metrics.yaml | Updates OTEL SDK metric attribute reference to rpc.status_code. |
| model/mcp/deprecated/common-deprecated.yaml | Updates MCP deprecated conventions to reference rpc.status_code. |
| docs/rpc/rpc-spans.md | Updates RPC spans doc tables/prose to use rpc.status_code. |
| docs/rpc/rpc-metrics.md | Updates RPC metrics doc tables/prose to use rpc.status_code. |
| docs/rpc/json-rpc.md | Updates JSON-RPC doc tables/prose to use rpc.status_code. |
| docs/rpc/grpc.md | Updates gRPC doc tables/prose to use rpc.status_code. |
| docs/rpc/dubbo.md | Updates Dubbo doc tables/prose to use rpc.status_code. |
| docs/rpc/connect-rpc.md | Updates Connect-RPC doc tables/prose to use rpc.status_code. |
| docs/registry/attributes/rpc.md | Updates generated registry docs to show rpc.status_code as current and rpc.response.status_code as deprecated. |
| docs/otel/sdk-metrics.md | Updates OTEL SDK metrics documentation to reference rpc.status_code. |
| docs/non-normative/rpc-migration.md | Updates migration guidance to the new attribute name (but currently loses the intermediate historical step from prior versions). |
| docs/non-normative/compatibility/grpc.md | Updates the gRPC compatibility mapping to reference rpc.status_code. |
| .chloggen/3919.yaml | Adds breaking-change changelog entry for the rename. |
Comments suppressed due to low confidence (2)
docs/non-normative/rpc-migration.md:120
- These metric migration tables now say "New:
rpc.status_code" in #2920, but #2920 introducedrpc.response.status_code(as shown by the removed lines in this PR). Consider keeping the original "New" row and adding a separate rename row for this PR, to preserve the timeline for readers migrating across versions.
| New: `rpc.status_code` | [#2920](https://github.com/open-telemetry/semantic-conventions/pull/2920) | |
docs/non-normative/rpc-migration.md:152
- Same as above for the client metric table: keeping "New:
rpc.response.status_code" in #2920 and adding a separate rename row for this PR avoids losing the intermediate step for migrations.
| New: `rpc.status_code` | [#2920](https://github.com/open-telemetry/semantic-conventions/pull/2920) | |
trask
approved these changes
Jul 23, 2026
trask
reviewed
Jul 23, 2026
lmolkova
moved this from Untriaged
to Needs More Approval
in Semantic Conventions Triage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3870
Based on the analysis in the issue:
resposenamespace to stay consistent with http and db. In HTTP status IS part of response, in SQL SQLSTATE is also part of response. And there it makes sense.Merge requirement checklist
Footnotes
Yes, I can answer maintainer questions about the content of this PR without using AI. ↩